Repository navigation
Document module-level AI involvement and provenance - #191
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
stdVBA needs scoped module-level AI disclosure: a legacy class with an AI-written fix must not be described as wholly AI-made. Add
@ai,@aidateand@aidescguidance, source metadata and generated documentation.@aidaterecords the earliest evidenced AI contribution to retained work, using an edit timestamp or matched commit date; it is not proof that earlier AI use never occurred.@aidescidentifies the AI-written changes, older/upstream work that is not attributed to AI, and uncertainty about human scrutiny.@aimark because W/X remains unresolved. The other 73 modules lack sufficient authorship evidence.The audit in docs/ai-provenance.json covers all 94 source modules. Class-name searches span every line of 43 indexed Codex logs, all 53 Cursor workspace headers/composer bodies/stored messages (including seven explore subagents), and 40 available Cursor transcript files. Blame on baseline 8ec0a13, author/committer dates and commit diffs were cross-checked against conversations for all 21 disclosed classes. Direct edits, implementation workflows and PR-only provenance are distinguished. One untitled Cursor record has no stored messages. Disclosure/history-lookup conversations, copied upstream code and unmerged experiments are not used to infer current AI authorship. No private transcripts, local identifiers or billing data are published.
VBDocsGen validates marks, real ISO calendar dates, nonempty descriptions and duplicate module tags, exposing optional ai, aiDate and aiDescription fields. Validation passed for all four marks, valid/invalid leap dates, malformed dates, empty descriptions, duplicate tags, absent marks and unresolved classifications. Generated docs preserve existing API members, signatures, descriptions and examples. All source/audit/generated metadata agree; full-PR VBA changes are comments only. UTF-8, CRLF byte checks and whitespace checks passed. Existing unrelated generator warnings remain. No Office tests/settings changes were needed.
Compatibility: no breaking changes identified. VBA APIs/runtime behavior are unchanged; docs.json gains optional metadata fields.
Created with gpt-6.1-sol in T3 Code (Codex harness).
AI descriptions use direct declarations of AI use, manual review and component scope. Retrospective methods and provenance qualifications stay in the audit, rather than in module descriptions. Classification marks and dates are unchanged by this wording pass.